home *** CD-ROM | disk | FTP | other *** search
-
-
-
- aaaarrrrrrrraaaayyyydddd((((1111mmmm)))) aaaarrrrrrrraaaayyyydddd((((1111mmmm))))
-
-
-
- NNNNAAAAMMMMEEEE
- arrayd - array services daemon
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- aaaarrrrrrrraaaayyyydddd [_o_p_t_i_o_n_s]
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- _a_r_r_a_y_d is the array services daemon. It performs several different tasks
- related to the use of an array of two or more machines, such as:
-
- - Allocating global array session handles
-
- - Forwarding "array commands" to all of the machines in an array
-
- - Maintaining a database of the current array configuration and providing
- that information to other commands and programs
-
- - Determining which processes belong to a particular array session and
- providing that information to other commands and programs
-
- For more discussion of these services, see _a_r_r_a_y__s_e_r_v_i_c_e_s(5).
-
- The _a_r_r_a_y_d command itself has several command line options. The valid
- options include:
-
- _----_cccc "Check": causes arrayd to read any configuration files then exit
- immediately, sending any errors to stderr rather than syslog
- (which is the usual behavior). This is primarily of use for
- checking the validity of new configuration files. This is the
- same as the _----_qqqq_ffff flag.
-
- _----_ffff _f_i_l_e_n_a_m_e
- Specifies the name of a single configuration file. This option
- may be specified more than once, in which case the files will be
- processed in the order that they are specified. One reason to
- have multiple configuration files would be to allow all of the
- machines in an array to use a single file (accessed via NFS,
- perhaps) for array entries and still maintain private
- configuration files for local options and/or security information.
- The format of an arrayd configuration file is described in
- _a_r_r_a_y_d._c_o_n_f(4). If no configuration files are specified, then
- "/usr/lib/array/arrayd.conf" and "/usr/lib/array/arrayd.auth" will
- both be used (in that order).
-
- _----_mmmm _n_u_m_b_e_r
- Sets the "machine identifier" used by the array services daemon
- for generating global array session handles to _n_u_m_b_e_r. Certain
- versions of the IRIX kernel may also use this value when
- generating array session handles. _n_u_m_b_e_r must be a value between
- 0 and 32767. It will override any IDENT setting in the LOCAL
- section of any configuration file.
-
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-
-
-
- aaaarrrrrrrraaaayyyydddd((((1111mmmm)))) aaaarrrrrrrraaaayyyydddd((((1111mmmm))))
-
-
-
- _----_nnnn Ordinarily, arrayd will automatically "daemonize" itself, that is,
- dissociate itself from the current terminal and place itself in
- the background. Specifying this option will cause arrayd to run
- in the foreground on the current terminal. This is mostly useful
- for testing purposes.
-
- _----_nnnn_ffff Do not read any configuration files. This is most useful with
- options like _----_ssss_mmmm that cause _a_r_r_a_y_d to quit after performing tasks
- that do not require configuration information. _----_nnnn_ffff will override
- any _----_ffff options.
-
- _----_nnnn_mmmm Do not set the system machine ID. This is used to override a
- "LOCAL OPTIONS SETMACHID" statement in the configuration file.
-
- _----_pppp _n_u_m_b_e_r
- This specifies which port the array services daemon should listen
- on for requests. It will override any PORT setting in the LOCAL
- section of any configuration file.
-
- _----_qqqq_ffff Quit after parsing the configuration file(s). This is the same as
- the _----_cccc option.
-
- _----_qqqq_mmmm Quit after setting the system machine ID. Causes _a_r_r_a_y_d to exit
- as soon as it has set the system machine identifier (or would have
- done so, in the case where this operation is not supported by the
- current OS release). This may be useful in cases where a non-
- default system machine identifier is desired, but none of the
- other array services provided by _a_r_r_a_y_d are needed. This can also
- be used to change the machine identifier on a system that is
- already running another copy of _a_r_r_a_y_d; in this case, kernel-
- generated array session handles will use the new machine
- identifier while those generated by _a_r_r_a_y_d will continue to use
- the original machine identifier.
-
- _----_ssss_mmmm Some versions of IRIX permit setting a system "machine
- identifier", which is used by the kernel for generating global
- array session handles. If the current system has this facility
- and _----_ssss_mmmm is specified, _a_r_r_a_y_d will set the machine ID to the value
- specified by a LOCAL IDENT statement in the configuration file or
- on the command line using the _----_mmmm option.
-
- _----_vvvv "Verbose": the daemon will run in the foreground (as with the -n
- option) and will send any error messages, plus some additional
- messages, to stderr rather than syslog. Specifying this option
- more than once or specifying more than one "v" (for example "-
- vvv") will cause additional debugging information to be generated.
-
- NNNNOOOOTTTTEEEESSSS
- _a_r_r_a_y_d can be set up to run automatically at system initialization time
- by using the _c_h_k_c_o_n_f_i_g(1M) command to turn on the aaaarrrrrrrraaaayyyy feature:
-
-
-
-
-
- PPPPaaaaggggeeee 2222
-
-
-
-
-
-
- aaaarrrrrrrraaaayyyydddd((((1111mmmm)))) aaaarrrrrrrraaaayyyydddd((((1111mmmm))))
-
-
-
- _cccc_hhhh_kkkk_cccc_oooo_nnnn_ffff_iiii_gggg _aaaa_rrrr_rrrr_aaaa_yyyy _oooo_nnnn
-
-
- When run in this manner, _a_r_r_a_y_d will take its command line options from
- the file /etc/config/arrayd.options.
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- array(1), arrayd.conf(4), array_services(5).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 3333
-
-
-
-